Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

conn: check we can use compression in startup #1215

Merged
merged 3 commits into from
Oct 12, 2018

Conversation

Zariel
Copy link
Contributor

@Zariel Zariel commented Oct 11, 2018

If the user asks to use compression check that the remote server
supports it by making an options call first.

Rejig conn startup to be self contained.

fixes #1205

If the user asks to use compression check that the remote server
supports it by making an options call first.

Rejig conn startup to be self contained.
Copy link
Contributor

@alourie alourie left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good, only one comment.

m["COMPRESSION"] = compressor
break
}
}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

if we're out of the for loop, but m["COMPRESSION"] is not set, then probably not supported by the backend. So, I reckon, reset s.conn.compressor here to nil, and print something appropriate in the log.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

actually, no, ignore. Not overly important to reset it, as probably the coordinator does startup only once.

m["COMPRESSION"] = compressor
break
}
}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

actually, no, ignore. Not overly important to reset it, as probably the coordinator does startup only once.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Azure Cosmos DB Cassandra API support
2 participants